Identifying technical vocabulary
نویسندگان
چکیده
منابع مشابه
Identifying the technical requirements for designing health portals
Aim: Considering technical requirements in the design of health portals increases the validity of information. This study identified the technical and content structure required to create these portals. Methods: This was a qualitative study which was conducted in 2020. A combination of comprehensive review and interview was used. The search was performed in Elsevier, EBSCO, Scopus, Web of Scie...
متن کاملTermight: Identifying and Translating Technical Terminology
We propose a semi-automatic tool, ter-might, that helps professional translators and terminologists identify technical terms and their translations. The tool makes use of part-of-speech tagging and word-alignment programs to extract candidate terms and their translations. Although the extraction programs are far from perfect, it isn't too hard for the user to filter out the wheat from the chaff...
متن کاملIdentifying Paraphrases between Technical and Lay Corpora
In previous work, we presented a preliminary study to identify paraphrases between technical and lay discourse types from medical corpora dedicated to the French language. In this paper, we test the hypothesis that the same kinds of paraphrases as for French can be detected between English technical and lay discourse types and report the adaptation of our method from French to English. Starting...
متن کاملIdentifying codes in ( random ) geometric networks ∗ ( Technical report version )
It is important for networks built from wireless sensors technology to have a functional location detection system. Identifying codes, first introduced to model fault diagnosis of multi-processor systems, have recently proved to be useful to address this question. We are interested in the situation where the area of communication of each sensor is modelled by a disk: thus we consider identifyin...
متن کاملAssessing technical debt by identifying design flaws in software systems
4 Tough time-to-market constraints and unanticipated integration or 5 evolution issues lead to design tradeoffs that usually cause flaws in 6 the structure of a software system. Thus, maintenance costs grow 7 significantly. The impact of these design decisions, which provide 8 short-term benefits at the expense of the system_s design integrity, is 9 usually referred to as technical debt. In thi...
متن کاملذخیره در منابع من
با ذخیره ی این منبع در منابع من، دسترسی به آن را برای استفاده های بعدی آسان تر کنید
ژورنال
عنوان ژورنال: System
سال: 2004
ISSN: 0346-251X
DOI: 10.1016/j.system.2003.11.008